Integrated collaborative user interface for a document editor program

ABSTRACT

An integrated collaborative user interface for a document editor is provided. The integrated collaborative user interface includes a document pane, document details pane and a section details pane. Document details and section details are obtained and provided to authors. A collaborative author views the document details, section details and provides updates to a document in the document editor. Changes are then refreshed to the authors to provide a consistent and up-to-date status of the document.

RELATED APPLICATIONS

This application is a continuation of and claims priority to applicationSer. No. 11/824,560, filed Jun. 29, 2007, entitled IntegratedCollaborative User Interface for a Document Editor Program, which ishereby incorporated by reference.

BACKGROUND

Document authoring projects may require multiple authors each workingfrom separate computing stations. One author may prepare a first portionof the document and another author may prepare another portion of thedocument. The portions are then spliced together by an editor to form asingle document. This type of collaborative authoring may include eachof the authors checking-out a document to add content and checking-in adocument when changes are complete. The checking-out and checking-inprocess may cause conflicts, restrict document availability for theauthors, and cause document status confusion.

In other situations, drafts of documents are circulated by email andcause excessive versioning. Commenting format does not exist in emails,so an author may include comments in the email, add comments to anattached document, comment through highlighting, or simply make changeswithout identifying what has been changed. Such emailing of draftscauses excessive circulation, tracking issues, lost drafts,mismanagement, and loss of productivity.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key and/oressential features of the claimed subject matter. Also, this Summary isnot intended to limit the scope of the claimed subject matter.

Aspects of the disclosure pertain to an integrated collaborative userinterface for a document editor program. The integrated collaborativeuser interface includes a document pane, document details pane and asection details pane. Document details and section details are obtainedand provided to authors. An author views the document details, views thesection details and provides updates to a document in the documenteditor program. Changes are then refreshed to provide a consistent andup-to-date status of the document.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments of the present invention aredescribed with reference to the following figures, wherein likereference numerals refer to like parts throughout the various viewsunless otherwise specified.

FIG. 1 represents one exemplary and generalized system overview forcollaborative authoring;

FIG. 2 represents general editor features of an integrated collaborativeuser interface for a document editor program;

FIG. 3 represents document details of an integrated collaborative userinterface for a document editor program;

FIG. 4 represents section details of an integrated collaborative userinterface for a document editor program;

FIG. 5 represents selected section details of an integratedcollaborative user interface for a document editor program;

FIG. 6 represents notification features of an integrated collaborativeuser interface for a document editor program;

FIG. 7 represents general author features of an integrated collaborativeuser interface for a document editor program;

FIG. 8 represents author selected section details of an integratedcollaborative user interface for a document editor program;

FIG. 9 represents author document details of an integrated collaborativeuser interface for a document editor program;

FIG. 10 represents a section status update feature of an integratedcollaborative user interface for a document editor program;

FIG. 11 represents a refresh feature of an integrated collaborative userinterface for a document editor program;

FIG. 12 represents a publish feature of an integrated collaborative userinterface for a document editor program;

FIG. 13 represents a published document of an integrated collaborativeuser interface for a document editor program;

FIG. 14 represents an operational flow diagram for generating editordata for collaborative authoring;

FIG. 15 represents an operational flow diagram for generating authordata for collaborative authoring;

FIG. 16 represents an operational flow diagram for publishing a documentassociated with collaborative authoring; and

FIG. 17 represents an exemplary computing device.

DETAILED DESCRIPTION

Embodiments are described more fully below with reference to theaccompanying drawings, which form a part hereof, and which show specificexemplary embodiments. However, embodiments may be implemented in manydifferent forms and should not be construed as limited to theembodiments set forth herein; rather, these embodiments are provided sothat this disclosure will be thorough and complete, and will fullyconvey the scope. Embodiments may be practiced as methods, systems ordevices. Accordingly, embodiments may take the form of an entirelyhardware implementation, an entirely software implementation or animplementation combining software and hardware aspects. The followingdetailed description is, therefore, not to be taken in a limiting sense.

The logical operations of the various embodiments are implemented (1) asa sequence of computer implemented steps running on a computing systemand/or (2) as interconnected machine modules within the computingsystem. The implementation is a matter of choice dependent on theperformance requirements of the computing system implementing theinvention. Accordingly, the logical operations making up the embodimentsdescribed herein are referred to alternatively as operations, steps ormodules.

Aspects of the disclosure pertain to an integrated collaborative userinterface for a document editor program. A document editor program isprovided that includes a collaborative user interface integrated withthe document editor program. The collaborative user interface may beaccessed from a ribbon tab. The collaborative user interface includes adocument pane where an author or editor may generate a document. Thecollaborative user interface may also include a document assembly pane.The document assembly pane includes document details and sectiondetails. The document details pane may include the owner of thedocument, the filename of the document, and an abstract of the document.The section details include various sections of the document along withthe author assigned to the section. The section details may be expandedto ascertain the status of each of the sections. Upon refreshing thedocument, the sections are updated with the most current content andstatus from the authors. As such, author and editors are provided aseamless user experience during collaboration with the document editorprogram. Multiple authors may edit the contents of different sections ofthe same document at the same time. Efficiency is increased because thestatus and content are updated upon refresh. Authors and editors mayeasily view the entirety of the document even when the document is in adraft state.

FIG. 1 represents one exemplary and generalized system overview forcollaborative authoring. System 100 includes editor 102, and author(s)104 and reader 106. Editor 102 and author(s) 104 may include a computingenvironment as depicted in FIG. 17 below. Editor 102 generates acollaborative authoring notification indicating that a document has beengenerated for collaborative authoring. Author(s) 104 collaborate on thedocument in accordance with the document and section details generatedby editor 102. Author(s) 104 submit additions to the document and updatethe status for the document sections. Reader 106 is a participant who isallowed read-only access to the collaboration process. Upon refreshing,reader 106, editor 102 and author(s) 104 may view an updated document.In other aspects, reader 106, editor 102 and author(s) 104 may view anupdated document according to viewing privileges. Features of theintegrated collaborative user interface are more fully set forth below.

FIG. 2 represents general editor features of an integrated collaborativeuser interface for a document editor program. Document editor 200includes ribbon menu pane 202, document editing pane 204, and documentassembly pane 206. Ribbon menu pane 202 includes line of businessintegration ribbon 208. Line of business integration ribbon 208 includescollaborative authoring functionality so that an author/editor does notneed to navigate from document editor 200 to perform collaborativeauthoring. The functionality of a collaborative authoring environment isaccessible and integrated in the document editor program so that a usermay perform collaborative functions while preparing a document.

Line of business ribbon 208 includes relationship ribbon 210, workspaceribbon 212, document ribbon 214 and section ribbon 216. Relationshipribbon 210 includes a related items button and a view action panebutton. Workspace pane 212 includes a create new button. Document pane214 includes a publish button, a view details button, a refresh button,and a notify authors button. Section pane 216 includes an insert button,a delete button, a view details button, a previous button, and a nextbutton. The buttons associated with line of business ribbon 208,depicted in FIG. 2, are examples. Functionality associated with Line ofbusiness ribbon 208 may include any type of button or feature forcollaborative authoring and are not limited to those depicted in FIG. 2.

Upon receiving a selection of line of business ribbon 208, documentassembly pane 206 may be displayed in document editor 200. Documentassembly pane 206 includes document details pane 218. Document detailspane 218 may include metadata associated with a document generated forcollaborative authoring. Document details pane 218 may display the ownerof the document. For example, the owner may be an editor of the documentor a team leader for a group. Document details pane 218 may include afilename for the document and an abstract. The abstract may display atext blurb describing the content of the document. From document detailspane 218, an owner or assigned author may quickly tell who created thecollaborative document, the file name of the document and the generalsubject matter of the document.

Document assembly pane 206 may also include section details pane 220.Section details pane displays metadata associated with each section ofthe document. Section details pane 220 includes a title and an authorsection. Section details pane 220 displays the titles associated withthe document along with the author assigned to each title. In thismanner an editor or author may easily determine an assignment ofauthoring tasks. For example, section details pane 220 depicts foursections which correspond to sections of document 204. Each section maybe assigned an author responsible for the section. Even though document204 is depicted as several block sections, document 204 may be formattedas a word processing document utilizing a markup language (“ML”). The MLcorrelates the document sections with metadata associated with documentassembly pane 206.

Document assembly pane 206 may also include expanded section detailspane 222. The expanded sections details pane 222 may populate and/ordisplay metadata associated with a selected section. Expanded sectionsdetails pane 222 includes a section title, an author, a due date for theauthoring of the section, the status of the section, and instructionsfor authoring the section. As an example, the table of contents may beselected in section details pane 220. Upon selecting, expanded sectionsdetails pane 222 displays the section title as “Table of Contents.” Theauthor is displayed as the author selected for the section by the ownerof the document. The due date for the section is displayed. The statusof the section is displayed (e.g. unassigned, assigned, draft,completed, etc). Instructions for drafting may also be displayed. Inthis manner, an editor or author may easily generate a collaborativeauthoring document, assign a collaborative authoring document, update acollaborative authoring document, check status of a collaborativeauthoring document, refresh a collaborative authoring document andpublish a collaborative authoring document.

FIG. 3 represents document details of an integrated collaborative userinterface for a document editor program. Document editor 300 includesdocument details set-up interface 302. Document details set-up interface302 provides an editing interface for editing document level properties.Document details set-up interface 302 includes a description field forreceiving a description of the document. Document details set-upinterface 302 also includes an editor field for identifying the editorof the document. Document details set-up interface 302 may include afilename field for identifying the filename associated with thedocument. Document details set-up interface 302 also includes a pathfield for receiving a path associated with a workspace in a multi-userenvironment. Document details set-up interface 302 may also include anabstract field for receiving an abstract of the document. After thefields are populated or changed, the received data may be displayed inassociation with document assembly pane 304.

FIG. 4 represents section details of an integrated collaborative userinterface for a document editor. Document editor 400 includes sectiondetails set-up interface 402. Section details set-up interface 402provides an editing interface for editing section level properties.Section details set-up interface 402 includes a section title field forreceiving a title for a section of the document. Section details set-upinterface 402 includes a section owner field for assigning an author forthe section. Section details set-up interface 402 includes a start datefield for receiving data associated with the start of an authoringproject. Section details set-up interface 402 includes a due date fieldfor setting a completion date for the section or project. Sectiondetails set-up interface 402 includes a status field for indicating astatus of the section (e.g. assigned, unassigned, draft, completed,etc). Section details set-up interface 402 includes instructions fieldfor receiving instructions to associate with the section duringauthoring. Section details set-up interface 402 includes reassignmentfield which either locks or opens reassignment functionality for aneditor or author. For example, an editor may assign a section to a firstauthor and then later reassign the section to a second author. Asanother example, an editor may assign a section to a team leader authorand the team leader author may reassign the section to a team member.Section details set-up interface 402 may include a view protectionfield. The view protection field may be set to restrict access of thesection. For example, the editor may assign section 1 to author 1. Theeditor may not want author 2 to view section 1. The editor may set asection view restriction on section 1 so that author 2 cannot seesection 1 of the document. As another example, the view protection fieldmay lock the document for editing except for sections the user hasrights to edit. As such, authors would not be able to edit sections notassigned to them and readers would not be able to edit the documentsections. In other cases, a section may be flagged as hidden so thatusers granted read access can see the content while users not grantedaccess cannot. Section details set-up interface 402 may also include anotification history field that indicates when the assigned author wasassigned the section. After the fields are populated or changed, thereceived data may be displayed in association with document assemblypane 404.

FIG. 5 represents selected section details of an integratedcollaborative user interface for a document editor program. Documenteditor 500 includes section detail pane 502. When a title of thedocument is selected, document editor 500 navigates to the respectiveportion of document 504. For example, a user may be on page 50 ofdocument 504. The user may desire viewing the progression of an assignedauthor in association with the table of contents. By selecting the tableof contents in section details pane 502, the editor table of contentsportion of the document is automatically displayed.

FIG. 6 represents notification features of an integrated collaborativeuser interface for a document editor program. Document editor 600includes notification interface 602. Notification interface 602 includessection status field which includes a summary of the status of thesections of the document. Notification interface 602 also includes filename field for identifying the file name of the document. Notificationinterface 602 also includes notification field for sending notificationsto authors assigned to sections.

FIG. 7 represents general author features of an integrated collaborativeuser interface for a document editor program. Document editor 700includes a document editor of an author after the author has beennotified that the editor has implemented collaborative authoring.Document editor 700 includes similar functionality and panes as FIG. 2.Document editor 700 includes document assembly pane 702. Documentassembly pane 702 includes the metadata set by the owner of thedocument. From document assembly pane 702 a collaborative author mayeasily determine what sections have been assigned to the author, the duedate of the sections, the status of the sections, an abstract of thedocument, and any instructions for completing the section. In oneaspect, document assembly pane 702 displays the authors assigned tosections of the document. In another aspect, document assembly pane 702displays all of the assignments and the authors for the assignments. Instill another aspect, the author has limited access to the document.

FIG. 8 represents author selected section details of an integratedcollaborative user interface for a document editor program. Documenteditor 800 includes section detail pane 802. When an author selects atitle of the document, document editor 800 navigates to the respectiveportion of document 804. In one aspect, the section details metadatathat the editor associated with the section are displayed to the author.In this manner, the author may easily determine the purpose of thesection.

FIG. 9 represents author document details of an integrated collaborativeuser interface for a document editor program. Document editor 900includes document details set-up interface 902. When the author isfinished drafting the section, the author may access document detailsset-up interface 902 and change the status of the document. For example,the author may change the status of the document from “assigned” to“draft.”

FIG. 10 represents a section status update feature of an integratedcollaborative user interface for a document editor program. Documenteditor 1000 includes notification pane 1002. Notification pane 1002includes a section status field for indicating the status of thesection. Notification pane 1002 also includes a save field for saving anew status of the section. Once the section is saved, a notification maybe sent to the editor/authors that the status of the section has beenchanged.

FIG. 11 represents a refresh feature of an integrated collaborative userinterface for a document editor program. Document editor 1100 mayinclude features of the collaborative user interface when aneditor/author refreshes the document. Refresh button 1102 is selected.Document 1104 automatically populates with updated content associatedwith sections that have been changed during an authoring period. In thismanner, an editor may easily refresh a document to determine the currentstate of the document. As depicted in FIG. 11, table of contents section1106 is updated to include the content the author generated. The refreshfeature may be implemented from either the authors interface or theeditors interface.

FIG. 12 represents a publish feature of an integrated collaborative userinterface for a document editor program. Document editor 1200 mayincludes features of the collaborative user interface when an editorpublishes the document. Publish button 1202 is selected.

FIG. 13 represents a published document of an integrated collaborativeuser interface for a document editor program. Document editor 1300includes published document 1302. When the document is published, thedocument assembly pane may be removed from document editor 1300 toprovide an optimized view of the published document. Also, line ofbusiness ribbon 1304 may be disabled to indicate that the user interfaceis no longer in a collaborative mode.

FIG. 14 represents an operational flow diagram for generating editordata for collaborative authoring. Operational flow 1400 may representoperations associated with an editor setting up collaborative authoringon an integrated collaborative user interface. Operational flow 1400begins at start operation 1402 and continues to operation 1404 wherecollaborative authoring is initiated. In one aspect, a line of businessribbon is actuated to initiate collaborative authoring. In anotheraspect, collaborative authoring is initiated from a menu.

Operational flow 1400 continues to operation 1406 where businessintegration tools are displayed. As depicted in FIG. 2, businessintegration tool may include a line of business integration ribbon and adocument assembly pane. Operational flow 1400 continues to operation1408 where document detail information is obtained. Document details mayinclude details as depicted in FIG. 3. Operational flow 1400 continuesto operation 1410 where the document details pane is populated withobtained document details information.

Operational flow 1400 continues to operation 1412 where section detailsinformation is obtained. Section details may include details as depictedin FIG. 4. Operational flow 1400 continues to operation 1414 where thesection details pane is populated with obtained section detailsinformation. At operation 1416, the authors associated with the sectionsare notified that they have been selected for collaborative authoring ofa document. Operational flow 1400 ends at end operation 1418.

FIG. 15 represents an operational flow diagram for generating authordata for collaborative authoring. Operational flow 1500 may representoperations associated with an author collaboratively authoring inassociation with an integrated collaborative user interface. Operationalflow 1500 begins at start operation 1502 and continues to operation 1504where a collaborative authoring notification is obtained. At operation1506, the document assembly pane of the author is populated with thedocument and section metadata in accordance with the metadata input bythe editor. Operational flow 1500 continues to operation 1508 where theauthor drafts the assigned section of the document. When the draft isfinished, the status of the document is updated as shown by operation1510. Operational flow 1500 continues to operation 1512 where theupdated document and document status are stored. The editor and/or otherauthors may be sent a notification indicating the update. Operationalflow 1500 continues to end operation 1514.

FIG. 16 represents an operational flow diagram for publishing a documentassociated with collaborative authoring. Operational flow 1600 mayrepresent operations associated with an editor after the editor hasreceived a notification that the status of one or more sections haschanged. Operational flow 1600 begins at start operation 1602 andcontinues to operation 1604 where a status update notification isobtained. At operation 1606, the content is refreshed and the updatedcontent is displayed in the document as indicated by operation 1608. Atoperation 1610, the document is published and at operation 1612 the lineof integration tools are disabled. Operation flow 1600 continues to endoperation 1614.

As set forth herein, the integrated collaborative user interface allowsmultiple authors to edit the content of different sections of the samedocument in parallel. The changes may be submitted at any time and thechanges may be received by one or more of the authors. The integratedcollaborative interface provides custom actions for starting andmanaging collaborative authoring. An editor may assign various sectionsof the document to various authors. The integrated collaborative userinterface allows authors to see and modify the structures of a document.Properties may also be modified. Sections of the document may further bereassigned after they have been started. In other aspects, an author maysee the status of sections assigned to other authors. Integratedcollaborative user interfaces also provide context-relevantnotifications. An editor has the ability to shut down collaboration atany time to stop further access to a document. Authors also have theability to work offline when documents are cached on the computingdevice of the author. As such, an integrated collaborative userinterface provides increased authoring productivity.

Referring to FIG. 17, an exemplary system for implementing the inventionincludes a computing device, such as computing device 1700. In a basicconfiguration, computing device 1700 may include any type of stationarycomputing device or a mobile computing device. Computing device 1700typically includes at least one processing unit 1702 and system memory1704. Depending on the exact configuration and type of computing device,system memory 1704 may be volatile (such as RAM), non-volatile (such asROM, flash memory, and the like) or some combination of the two. Systemmemory 1704 typically includes operating system 1705, one or moreapplications 1706, and may include program data 1707. In one embodiment,applications 1706 further include application 1720 for maildistribution. This basic configuration is illustrated in FIG. 17 bythose components within dashed line 1708.

Computing device 1700 may also have additional features orfunctionality. For example, computing device 1700 may also includeadditional data storage devices (removable and/or non-removable) suchas, for example, magnetic disks, optical disks, or tape. Such additionalstorage is illustrated in FIG. 17 by removable storage 1709 andnon-removable storage 1710. Computer storage media may include volatileand non-volatile, removable and non-removable media implemented in anymethod or technology for storage of information, such as computerreadable instructions, data structures, program modules or other data.System memory 1704, removable storage 1709 and non-removable storage1710 are all examples of computer storage media. Computer storage mediaincludes, but is not limited to, RAM, ROM, EEPROM, flash memory or othermemory technology, CD-ROM, digital versatile disks (DVD) or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store the desired information and which can be accessed bycomputing device 1700. Any such computer storage media may be part ofdevice 1700. Computing device 1700 may also have input device(s) 1712such as a keyboard, mouse, pen, voice input device, touch input device,etc. Output device(s) 1714 such as a display, speakers, printer, etc.may also be included.

Computing device 1700 also contains communication connection(s) 1716that allow the device to communicate with other computing devices 1718,such as over a network or a wireless network. Communicationconnection(s) 1716 is an example of communication media. Communicationmedia typically embodies computer readable instructions, datastructures, program modules or other data in a modulated data signalsuch as a carrier wave or other transport mechanism and includes anyinformation delivery media. The term “modulated data signal” may includea signal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media may include wired media such asa wired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. The term computerreadable media as used herein includes both storage media andcommunication media.

Although the invention has been described in language that is specificto structural features and/or methodological steps, it is to beunderstood that the invention defined in the appended claims is notnecessarily limited to the specific features or steps described. Rather,the specific features and steps are disclosed as forms of implementingthe claimed invention. Since many embodiments of the invention can bemade without departing from the spirit and scope of the invention, theinvention resides in the claims hereinafter appended.

1. A method for providing notifications to collaborators of a document,comprising: accessing a document editor program that includescollaborative authoring functionality for collaboration andcommunication on the document and an integrated collaborative userinterface that is used to display information relating to thecollaboration; using the integrated collaborative user interface toassociate collaborators with one or more sections of the document for atleast one of: reviewing the one or more sections and updating the one ormore sections, wherein more than one collaborator can be associated witha same section; receiving an update to the document as a result of aninput made by at least one of the collaborators; sending a notificationof the update to the document to at least one of: a new collaborator andan existing collaborator of the document; and refreshing the document toreflect the update.
 2. The method of claim 1, further comprisingdisplaying a notification interface that displays information relatingto sending the notification.
 3. The method of claim 1, wherein sendingthe notification of the update comprises sending the notification of theupdate in response to receiving an input from the collaborative userinterface.
 4. The method of claim 1, further comprising refreshing adisplay of the collaborative user interface to display an updated statusof the document based on updates made to the document by at least one ofthe collaborators of the document.
 5. The method of claim 1, whereinsending the notification is sent in response to an editing session beingfinished by at least one of the collaborators.
 6. The method of claim 1,further comprising hiding a display of the information relating to thecollaboration from a display of the document.
 7. The method of claim 1,wherein sending the notification of the update to the document comprisessending a context-relevant notification.
 8. The method of claim 1,wherein an update is made to the document from at least one of thecollaborators that is offline.
 9. The method of claim 1, furthercomprising preventing a display of a portion of the collaborativeinformation to at least one of the collaborators based on assignedpermissions.
 10. A computer storage media having computer executableinstructions for providing notifications to collaborators of a document,the instructions comprising: accessing a document editor program thatincludes collaborative authoring functionality for collaboration andcommunication on the document and an integrated collaborative userinterface that is used to display information relating to thecollaboration; a collaborator adding other collaborators to participatein reviewing the document, wherein at least a portion of thecollaborators are associated with a same section of the document;receiving updates to the document as a result of input made by at leasttwo of the collaborators; updating the integrated collaborative userinterface in response to the updates; determining one or morecollaborators to receive a notification of at least one of the updates;sending a notification of at least one of the updates to the document tothe determined collaborators; and refreshing the document to reflect theupdates.
 11. The computer storage media of claim 10, further comprisingautomatically refreshing a display of the collaborative user interfaceto display an updated status of the document based on the updates madeto the document.
 12. The computer storage media of claim 10, furthercomprising hiding a portion of the display of the information relatingto the collaboration from a display of the document.
 13. The computerstorage media of claim 12, further comprising receiving a selection froma user indicating the portion of the display of to hide.
 14. Thecomputer storage media of claim 10, wherein sending the notification ofthe update to the document comprises sending a context-relevantnotification.
 15. The computer storage media of claim 10, wherein eachof the collaborators can update the document in parallel.
 16. Thecomputer storage media of claim 10, wherein determining the one or morecollaborators to receive at least one of the notifications comprisesdetermining when a section is updated that is assigned to thecollaborator.
 17. A system for providing notifications to collaboratorsof a document, the system comprising: a processor; a display; a documenteditor program that includes collaborative authoring functionality forcollaboration and communication on the document and an integratedcollaborative user interface that is used to display informationrelating to the collaboration; and a memory having computer-executableinstructions stored thereon, the instructions being configured to:displaying the integrated collaborative user interface to addcollaborators to participate in collaboration and communication for thedocument; receiving an update to the document as a result of an inputmade by at least one of the collaborators; determining one or morecollaborators to receive a notification of the update, wherein the oneor more collaborators comprise at least one of: a new collaborator andan existing collaborator of the document; and sending a notification ofthe update to the document to the determined collaborators.
 18. Thesystem of claim 17, further comprising automatically refreshing adisplay of the collaborative user interface to display an updated statusof the document based on updates made in parallel to the document bycollaborators of the document.
 19. The system of claim 17, furthercomprising removing a display of the information relating to thecollaboration in response to a selection to the integrated collaborativeuser interface.
 20. The system of claim 17, wherein determining the oneor more collaborators to receive the notification of the updatecomprises determining assigned permissions for each of thecollaborators.